home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990725-20000114
/
000101_news@columbia.edu _Wed Sep 15 12:52:16 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2000-01-13
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA28223
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 15 Sep 1999 12:52:15 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id MAA25737
for kermit.misc@watsun.cc.columbia.edu; Wed, 15 Sep 1999 12:34:18 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: How do I pass Kermit parameters?
Date: 15 Sep 1999 16:34:16 GMT
Organization: Columbia University
Message-ID: <7rohq8$p46$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <FI3K15.E6F@fcshome.stoneham.ma.us>,
fred smith <fredex@fcshome.stoneham.ma.us> wrote:
: Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
: : In article <7rm5g7$v0a$1@nnrp1.deja.com>, <dixonan@my-deja.com> wrote:
: : : I want to pass Kermit parameters from my Visual Basic program.
: : : <snip>
: : The methods for passing command-line arguments to a script are a bit
: : awkward, since K95 (and C-Kermit 6.0, upon which it is based) have
: : their own command-line arguments. All of this will be simplified in the
: : next releases (C-Kermit 7.0 and K95 1.1.18), but for the time being, you
: : have two choices. The first one is:
:
: : <path>k95 <name-of-script-file> = <arg1> <arg2> ...
: <snip>
:
: What I've done, with both C-Kermit and MS-Kermit, when I had a whole
: bunch of things I wanted to pass to a kermit script was to put a (on
: Unix) shellscript or (or DOS) batchfile wrapper around the invocation of
: Kermit. This shellscript/batch file takes its own parameter list and/or
: things from its environment, and writes a kermit script which assigns
: those values to kermit variables, then as the last thing it does invokes
: kermit with appropriate arguments to cause kermit to 'take' that kermit
: script. (This tends to be a 3-stage operation: 1) run the batch file,
: which builds the kermit script, 2) invoke kermit which runs the
: newly-constructed script, and 3) that on-the-fly script then tends to
: invoke the "real" script, the one that actually does the work, once it
: has completed processing the various commands created on the fly by the
: batch file). This shellscript/batch file, then, is invoked from within
: some other program that wants to do some kind of complex thing with
: Kermit.
:
Like I said, (more than) a bit awkward! :-) In the new releases, you'll be
able to pass command-line arguments directly to the script and refer to
them directly within the script. You can see lots of examples in the
C-Kermit/K95 script library at:
http://www.columbia.edu/kermit/ckscripts.html
Also, the new versions let you have more than 10 arguments on the command
line. (And inq UNIX, you can even designate Kermit as the "shell" to execute
a script, so you can run a Kermit script exactly the same way you would run a
shell script.)
(We are working hard on the new releases and will release them as soon as
they are ready.)
- Frank